v10.49.0

Compare Source

Important Changes

• feat(browser): Add View Hierarchy integration (#​14981)

  A new viewHierarchyIntegration captures the DOM structure when an error occurs, providing a snapshot of the page state for debugging. Enable it in your Sentry configuration:

  import * as Sentry from '@​sentry/browser';
  
  Sentry.init({
    dsn: '__DSN__',
    integrations: [Sentry.viewHierarchyIntegration()],
  });

• feat(cloudflare): Split alarms into multiple traces and link them (#​19373)

  Durable Object alarms now create separate traces for each alarm invocation, with proper linking between related alarms for better observability.

• feat(cloudflare): Enable RPC trace propagation with enableRpcTracePropagation (#​19991, #​20345)

  A new enableRpcTracePropagation option enables automatic trace propagation for Cloudflare RPC calls via .fetch(), ensuring distributed traces flow correctly across service bindings.

• feat(core): Add enableTruncation option to AI integrations (#​20167, #​20181, #​20182, #​20183, #​20184)

  All AI integrations (OpenAI, Anthropic, Google GenAI, LangChain, LangGraph) now support an enableTruncation option to control whether large AI inputs/outputs are truncated.

• feat(opentelemetry): Vendor AsyncLocalStorageContextManager (#​20243)

  The OpenTelemetry context manager is now vendored internally, reducing external dependencies and ensuring consistent behavior across environments.

Other Changes

• feat(core): Export a reusable function to add tracing headers (#​20076)
• feat(core): Expose rewriteSources top level option (#​20142)
• feat(deps): bump defu from 6.1.4 to 6.1.6 (#​20104)
• feat(node-native): Add support for V8 v14 (Node v25+) (#​20125)
• feat(node): Include global scope for eventLoopBlockIntegration (#​20108)
• fix(core, node): Support loading Express options lazily (#​20211)
• fix(core): Set conversation_id only on gen_ai spans (#​20274)
• fix(core): Use ai.operationId for Vercel AI V6 operation name mapping (#​20285)
• fix(deno): Avoid inferring invalid span op from Deno tracer (#​20128)
• fix(deno): Handle reader.closed rejection from releaseLock() in streaming (#​20187)
• fix(nextjs): Preserve directive prologues in turbopack loaders (#​20103)
• fix(nextjs): Skip custom browser tracing setup for bot user agents (#​20263)
• fix(opentelemetry): Use WeakRef for context stored on scope to prevent memory leak (#​20328)
• fix(replay): Use live click attributes in breadcrumbs (#​20262)

Bundle size 📦

v10.48.0

Compare Source

v10.47.0

Compare Source

Important Changes

• feat(node-core): Add OTLP integration for node-core/light (#​19729)

  Added otlpIntegration at @sentry/node-core/light/otlp for users who manage
  their own OpenTelemetry setup and want to send trace data to Sentry without
  adopting the full @sentry/node SDK.

  import { NodeTracerProvider } from '@​opentelemetry/sdk-trace-node';
  import * as Sentry from '@​sentry/node-core/light';
  import { otlpIntegration } from '@​sentry/node-core/light/otlp';
  
  const provider = new NodeTracerProvider();
  provider.register();
  
  Sentry.init({
    dsn: '__DSN__',
    integrations: [
      otlpIntegration({
        // Export OTel spans to Sentry via OTLP (default: true)
        setupOtlpTracesExporter: true,
      }),
    ],
  });

  The integration links Sentry errors to OTel traces and exports spans to Sentry via OTLP.

• feat(node, bun): Add runtime metrics integrations for Node.js and Bun (#​19923, #​19979)

  New nodeRuntimeMetricsIntegration and bunRuntimeMetricsIntegration automatically collect runtime health metrics and send them to Sentry on a configurable interval (default: 30s). Collected metrics include memory (RSS, heap used/total), CPU utilization, event loop utilization, and process uptime. Node additionally collects event loop delay percentiles (p50, p99). Extra metrics like CPU time and external memory are available as opt-in.

  // Node.js
  import * as Sentry from '@​sentry/node';
  
  Sentry.init({
    dsn: '...',
    integrations: [Sentry.nodeRuntimeMetricsIntegration()],
  });
  
  // Bun
  import * as Sentry from '@​sentry/bun';
  
  Sentry.init({
    dsn: '...',
    integrations: [Sentry.bunRuntimeMetricsIntegration()],
  });

• feat(core): Support embedding APIs in google-genai (#​19797)

  Adds instrumentation for the Google GenAI embedContent API, creating gen_ai.embeddings spans.

• feat(browser): Add elementTimingIntegration for tracking element render and load times (#​19869)

  The new elementTimingIntegration captures Element Timing API data as Sentry metrics. It emits element_timing.render_time and element_timing.load_time distribution metrics for elements annotated with the elementtiming HTML attribute.

  import * as Sentry from '@​sentry/browser';
  
  Sentry.init({
    dsn: '__DSN__',
    integrations: [Sentry.browserTracingIntegration(), Sentry.elementTimingIntegration()],
  });

  <img src="hero.jpg" elementtiming="hero-image" />

Other Changes

• feat(nuxt): Add middleware instrumentation compatibility for Nuxt 5 (#​19968)
• feat(nuxt): Support parametrized SSR routes in Nuxt 5 (#​19977)
• feat(solid): Add route parametrization for Solid Router (#​20031)
• fix(core): Guard nullish response in supabase PostgREST handler (#​20033)
• fix(node): Deduplicate sentry-trace and baggage headers on outgoing requests (#​19960)
• fix(node): Ensure startNewTrace propagates traceId in OTel environments (#​19963)
• fix(nuxt): Use virtual module for Nuxt pages data (SSR route parametrization) (#​20020)
• fix(opentelemetry): Convert seconds timestamps in span.end() to milliseconds (#​19958)
• fix(profiling): Disable profiling in worker threads (#​20040)
• fix(react-router): Disable debug ID injection in Vite plugin to prevent double injection (#​19890)
• refactor(browser): Reduce browser package bundle size (#​19856)
• feat(deps): Bump OpenTelemetry dependencies (#​20046)

Bundle size 📦

v10.46.0

Compare Source

Important Changes

• feat(elysia): @sentry/elysia - Alpha Release (#​19509)

  New Sentry SDK for the Elysia web framework, supporting both Bun and Node.js runtimes.

  Note: This is an alpha release. Please report any issues or feedback on GitHub.

  Features

  • Automatic error capturing — 5xx errors captured via global onError hook; 3xx/4xx ignored by default. Customizable with shouldHandleError.
  • Automatic tracing — Lifecycle spans for every Elysia phase (Request, Parse, Transform, BeforeHandle, Handle, AfterHandle, MapResponse, AfterResponse, Error) with parameterized route names (e.g. GET /users/:id).
  • Distributed tracing — sentry-trace and baggage headers propagated automatically on incoming/outgoing requests.

  Usage

  import * as Sentry from '@​sentry/elysia';
  import { Elysia } from 'elysia';
  
  Sentry.init({ dsn: '__DSN__', tracesSampleRate: 1.0 });
  
  const app = Sentry.withElysia(new Elysia());
  app.get('/', () => 'Hello World');
  app.listen(3000);

Other Changes

• feat(nuxt): Conditionally use plugins based on Nitro version (v2/v3) (#​19955)
• fix(cloudflare): Forward ctx argument to Workflow.do user callback (#​19891)
• fix(cloudflare): Send correct events in local development (#​19900)
• fix(core): Do not overwrite user provided conversation id in Vercel (#​19903)
• fix(core): Preserve .withResponse() on Anthropic instrumentation (#​19935)
• fix(core): Send internal_error as span status for Vercel error spans (#​19921)
• fix(core): Truncate content array format in Vercel (#​19911)
• fix(deps): bump fast-xml-parser to 5.5.8 in @​azure/core-xml chain (#​19918)
• fix(deps): bump socket.io-parser to 4.2.6 to fix CVE-2026-33151 (#​19880)
• fix(nestjs): Add node to nest metadata (#​19875)
• fix(serverless): Add node to metadata (#​19878)

Work in this release was contributed by @​roli-lpci. Thank you for your contributions!

Important Changes

• feat(node): Add nodeRuntimeMetricsIntegration for automatic Node.js runtime metrics (#​19923)

  The new nodeRuntimeMetricsIntegration automatically collects Node.js runtime health metrics and sends them to Sentry. Eight metrics are emitted by default every 30 seconds: memory (RSS, heap used/total), CPU utilization, event loop delay (p50, p99), event loop utilization, and process uptime. Additional metrics are available as opt-in.

  import * as Sentry from '@​sentry/node';
  
  Sentry.init({
    dsn: '...',
    integrations: [Sentry.nodeRuntimeMetricsIntegration()],
  });

v10.45.0

Compare Source

Important Changes

• feat(remix): Server Timing Headers Trace Propagation (#​18653)

  The Remix SDK now supports automatic trace propagation via Server-Timing response headers to continue pageload traces on the client side.
  This means, you no longer have to define a custom meta function to add Sentry <meta> tags to your page as previously.
  We'll update out Remix tracing docs after this release.

Other Changes

• fix(cloudflare): Use correct env types for withSentry (#​19836)
• fix(core): Align error span status message with core SpanStatusType for langchain/google-genai (#​19863)
• fix(deno): Clear pre-existing OTel global before registering TracerProvider (#​19723)
• fix(nextjs): Skip tracing for tunnel requests (#​19861)
• fix(node-core): Recycle propagationContext for each request (#​19835)
• ref(core): Simplify core utility functions for smaller bundle (#​19854)

v10.44.0

Compare Source

Important Changes

• feat(effect): Add @sentry/effect SDK (Alpha) (#​19644)

  This release introduces @sentry/effect, a new SDK for Effect.ts applications. The SDK provides Sentry integration via composable Effect layers for both Node.js and browser environments.

  Compose the effectLayer with optional tracing, logging, and metrics layers to instrument your Effect application:

  import * as Sentry from '@​sentry/effect';
  import * as Layer from 'effect/Layer';
  import * as Logger from 'effect/Logger';
  
  const SentryLive = Layer.mergeAll(
    Sentry.effectLayer({ dsn: '__DSN__', tracesSampleRate: 1.0, enableLogs: true }),
    Layer.setTracer(Sentry.SentryEffectTracer),
    Logger.replace(Logger.defaultLogger, Sentry.SentryEffectLogger),
    Sentry.SentryEffectMetricsLayer,
  );

  Alpha features are still in progress, may have bugs and might include breaking changes. Please reach out on GitHub if you have any feedback or concerns.

• feat(astro): Add Astro 6 support (#​19745)

  This release enables full support for Astro v6 by adjusting our Astro SDK's middleware to some Astro-internal
  changes. We cannot yet guarantee full support for server-islands, due to a bug in Astro v6
  but we'll follow up on this once the bug is fixed.

• feat(hono): Add basic instrumentation for Node runtime (#​19817)

  Adds a new package @sentry/hono/node (alpha) with basic instrumentation for Hono applications running in Node.js.
  The Hono middleware for Cloudflare (@sentry/hono/cloudflare - alpha) comes with fixes, and it's now possible to access the Cloudflare Worker Bindings (env) from the options' callback.

  Start using the new Hono middlewares by installing @sentry/hono and importing the respective middleware for your runtime.
  More instructions can be found in the Hono readme.

  Alpha features are still in progress, may have bugs and might include breaking changes. Please reach out on GitHub if you have any feedback or concerns.

• feat(nestjs): Instrument @nestjs/bullmq @Processor decorator (#​19759)

  Automatically capture exceptions and create transactions for BullMQ queue processors in NestJS applications.

  When using the @Processor decorator from @nestjs/bullmq, the SDK now automatically wraps the process() method
  to create queue.process transactions with proper isolation scopes, preventing breadcrumb and scope leakage between
  jobs and HTTP requests. Errors thrown in processors are captured with the auto.queue.nestjs.bullmq mechanism type.

  Requires @nestjs/bullmq v10.0.0 or later.

• feat(nestjs): Instrument @nestjs/schedule decorators (#​19735)

  Automatically capture exceptions thrown in @Cron, @Interval, and @Timeout decorated methods.

  Previously, exceptions in @Cron methods were only captured if you used the SentryCron decorator. Now they are
  captured automatically. The exception mechanism type changed from auto.cron.nestjs.async to
  auto.function.nestjs.cron. If you have Sentry queries or alerts that filter on the old mechanism type, update them
  accordingly.

• feat(node): Expose headersToSpanAttributes option on nativeNodeFetchIntegration() (#​19770)

  Response headers like http.response.header.content-length were previously captured automatically on outgoing
  fetch spans but are now opt-in since @opentelemetry/instrumentation-undici@0.22.0. You can now configure which
  headers to capture via the headersToSpanAttributes option.

  Sentry.init({
    integrations: [
      Sentry.nativeNodeFetchIntegration({
        headersToSpanAttributes: {
          requestHeaders: ['x-custom-header'],
          responseHeaders: ['content-length', 'content-type'],
        },
      }),
    ],
  });

Other Changes

• feat(browser/cloudflare): Export conversation id from browser and cloudflare runtimes (#​19820)
• feat(bun): Set http response header attributes instead of response context headers (#​19821)
• feat(core): Add sentry.timestamp.sequence attribute for timestamp tie-breaking (#​19421)
• feat(deno): Set http response header attributes instead of response context headers (#​19822)
• feat(deps): Bump OpenTelemetry dependencies (#​19682)
• feat(nestjs): Use more specific span origins for NestJS guards, pipes, interceptors, and exception filters (#​19751)
• feat(nextjs): Vercel queue instrumentation (#​19799)
• feat(node): Avoid OTEL instrumentation for outgoing requests on Node 22+ (#​17355)
• feat(deps): bump hono from 4.12.5 to 4.12.7 (#​19747)
• feat(deps): bump mysql2 from 3.14.4 to 3.19.1 (#​19787)
• feat(deps): bump simple-git from 3.30.0 to 3.33.0 (#​19744)
• feat(deps): bump yauzl from 3.2.0 to 3.2.1 (#​19809)
• fix(browser): Skip browserTracingIntegration setup for bot user agents (#​19708)
• fix(cloudflare): Recreate client when previous one was disposed (#​19727)
• fix(core): Align Vercel embedding spans with semantic conventions (#​19795)
• fix(core): Fallback to sendDefaultPii setting in langchain and langgraph in non-node environments (#​19813)
• fix(core): Improve Vercel AI SDK instrumentation attributes (#​19717)
• fix(hono): Align error mechanism (#​19831)
• fix(hono): Allow passing env and fix type issues (#​19825)
• fix(nestjs): Fork isolation scope in @nestjs/event-emitter instrumentation (#​19725)
• fix(nextjs): Log correct lastEventId when error is thrown in component render (#​19764)
• fix(nextjs): Strip sourceMappingURL comments after deleting source maps in turbopack builds (#​19814)
• fix(nuxt): Upload client source maps (#​19805)
• fix(profiling-node): Fix NODE_VERSION rendered as [object Object] in warning (#​19788)

v10.43.0

Compare Source

Important Changes

• feat(nextjs): Add Turbopack support for React component name annotation (#​19604)

  We added experimental support for React component name annotation in Turbopack builds. When enabled, JSX elements
  are annotated with data-sentry-component, data-sentry-element, and data-sentry-source-file attributes at build
  time. This enables searching Replays by component name, seeing component names in breadcrumbs, and performance
  monitoring — previously only available with webpack builds.

  This feature requires Next.js 16+ and is currently behind an experimental flag:

  // next.config.ts
  import { withSentryConfig } from '@​sentry/nextjs';
  
  export default withSentryConfig(nextConfig, {
    _experimental: {
      turbopackReactComponentAnnotation: {
        enabled: true,
        ignoredComponents: ['Header', 'Footer'], // optional
      },
    },
  });

• feat(hono): Instrument middlewares app.use() (#​19611)

  Hono middleware registered via app.use() is now automatically instrumented, creating spans for each middleware invocation.

Other Changes

• feat(node-core,node): Add tracePropagation option to http and fetch integrations (#​19712)
• feat(hono): Use parametrized names for errors (#​19577)
• fix(browser): Fix missing traces for user feedback (#​19660)
• fix(cloudflare): Use correct Proxy receiver in instrumentDurableObjectStorage (#​19662)
• fix(core): Standardize Vercel AI span descriptions to align with GenAI semantic conventions (#​19624)
• fix(deps): Bump hono to 4.12.5 to fix multiple vulnerabilities ([#​19653](https://redirect.github.com/getsentry/sentry-javascript/pull/1965